mtk_logger mtk_parse_info: Fix track start for Holux devices
authorStefan Bauer <stefan-a-bauer@gmx.net>
Thu, 14 Jan 2016 22:38:14 +0000 (23:38 +0100)
committerStefan Bauer <stefan-a-bauer@gmx.net>
Thu, 14 Jan 2016 22:38:14 +0000 (23:38 +0100)
commit31bd36c4a27edbf1f1593aac53c6e623c4407759
tree1cdc333cc6707bf18c1979e15ff868685d3f2580
parent585451ca54451b3417e3ce6f3dbc71e973e85864
mtk_logger mtk_parse_info: Fix track start for Holux devices

Previously, a new track was created when the event "GPS Logger turned on"
was read. This is correct for the MTK_LOGGER only, but not for the
Holux devices M241 & GR245.

Case #1: Firmware versions where the event is never logged. Effect: One large
track is created.
Applies to GR245 v1.x

Case #2: Firmware versions where the event is logged, but not
at the beginning of a track, but _after_ the first track point of a track
(at least most of the times).
Applies to GR245 v2.00, M241 v1.12, v1.13

For all of the currently known Holux firmware versions, the correct
indication of a track start is the "Log period change" /
"Log distance change" event.

This commit adds some more testcases (241 case provided by Erik Krause)
that were suffering from Case #2 before.

The existing 245 test is an example for Case #1 and has been fixed.
mtk_logger.cc
reference/track/mtk_logger_gp245.gpx
reference/track/mtk_logger_gp245_fw_v2.bin [new file with mode: 0644]
reference/track/mtk_logger_gp245_fw_v2.gpx [new file with mode: 0644]
reference/track/mtk_logger_m241_multiple_tracks.bin [new file with mode: 0644]
reference/track/mtk_logger_m241_multiple_tracks.gpx [new file with mode: 0644]
testo.d/mtk.test